Skip to main content

This is a new service – your feedback will help us to improve it.

Plymouth City Council

Tree preservation zone

There is a problem

  • tree-preservation-order column is missing values

1741

reference
1741
name
1741
tree-preservation-order

tree-preservation-order missing

tree-preservation-zone-type
woodland
geometry
MULTIPOLYGON (((-4.030470 50.377941,-4.030505 50.377975,-4.030553 50.378012,-4.030575 50.378026,-4.030623 50.378052,-4.030657 50.378067,-4.030732 50.378095,-4.030962 50.378141,-4.031119 50.378168,-4.031339 50.378193,-4.031453 50.378203,-4.031647 50.378215,-4.031724 50.378218,-4.032655 50.378219,-4.033372 50.378228,-4.033425 50.378221,-4.033478 50.378209,-4.033503 50.378201,-4.033538 50.378187,-4.033576 50.378166,-4.033582 50.378160,-4.033583 50.378155,-4.033583 50.378151,-4.033578 50.378142,-4.033569 50.378132,-4.033533 50.378111,-4.033517 50.378099,-4.033486 50.378069,-4.033478 50.378059,-4.033463 50.378036,-4.033419 50.377940,-4.033416 50.377929,-4.033416 50.377917,-4.033424 50.377881,-4.033448 50.377835,-4.033469 50.377802,-4.033378 50.377813,-4.033264 50.377822,-4.033198 50.377824,-4.033128 50.377820,-4.032999 50.377802,-4.032866 50.377786,-4.032822 50.377784,-4.032739 50.377786,-4.032574 50.377780,-4.032464 50.377788,-4.032414 50.377790,-4.032303 50.377786,-4.032271 50.377786,-4.032244 50.377788,-4.032000 50.377823,-4.031964 50.377826,-4.031723 50.377817,-4.031559 50.377804,-4.031487 50.377795,-4.031472 50.377788,-4.031448 50.377757,-4.030866 50.377788,-4.030470 50.377941)))
point
POINT (-4.032092 50.378001)
notes
Land South From Aycliffe Gardens Plymouth
entry-date
2024-12-13
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The Tree preservation zone guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that covers this zone.

How to improve Plymouth City Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL